Method of billing in an abbreviated dialing service

ABSTRACT

A telecommunications service translates an abbreviated dialing code into a toll free number, routes the call to an interexchange carrier, and manages the billing associated with the call. A billing system processes the billing such that a subscriber of the abbreviated dialing code service is billed for the call rather than a calling party.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.09/994,889, filed on Nov. 28, 2001, the content of which is incorporatedby reference herein in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of telecommunications. Moreparticularly, the present invention relates to translating anabbreviated dialing code into a ten digit number and managing thebilling associated with the call.

2. Acronyms

The written description provided herein contains acronyms that refer tovarious telecommunications services, components and techniques, as wellas features relating to the present invention. Although some of theseacronyms are known, use of these acronyms is not strictly standardizedin the art. For purposes of the written description herein, acronymswill be defined as follows:

-   -   Access Code (AC)    -   Advanced Intelligent Network (AIN)    -   Automatic Message Accounting (AMA)    -   Bellcore Automatic Message Accounting Format (BAF)    -   Carrier Access Billing System (CABS)    -   Carrier Identification Code (CIC)    -   Central Office (CO)    -   Customer Record and Information System (CRIS)    -   File Transport Protocol (FTP)    -   Free Billing Table (FBT)    -   Local Access and Transport Area (LATA)    -   Integrated Services Digital Network User Part (ISUP)    -   Interexchange Carrier (IXC)    -   Integrated Service Control Point (ISCP)    -   Off-Hook Delay (OHD)    -   Plain Old Telephone Service (POTS)    -   Public Office Dialing Plan (PODP)    -   Public Switched Telephone Network (PSTN)    -   Service Control Point (SCP)    -   Service Logic Program Identifier (slpID)    -   Service Management System (SMS)    -   Service Switching Point (SSP)    -   Signal Transfer Point (STP)    -   Signaling System 7 (SS7)    -   Transaction Capabilities Applications Protocol (TCAP)    -   Vertical Service Code (VSC)    -   Wide Area Network (WAN)

3. Description of Background Information

National advertisers and companies are continually seeking methods tosell their products to consumers. Putting the consumer in contact withthe seller is critical to the relationship between companies andconsumers. Previously, companies enticed consumers to call them using800 or 888 toll free telephone numbers, in which the caller was notcharged for the telephone call. However, consumers are not likely toremember the complete 800 or 888 numbers for every company they may wishto contact. As a result, it would be desirable to have an abbreviateddialing code that would allow callers to reach national advertisers.

Consumers would be more likely to place calls to an abbreviated dialingcode service if they would incur no costs associated with the calls.Such a service would bring advertisers and consumers together to eachother's benefit.

However, a significant problem associated with this type of serviceincludes billing calls originating from various states and LATAs. Asolution must be offered to see that charges are incurred by thesubscriber offering the abbreviated dialing code service based on thenumber of calls to the service regardless of the billing system used inthe state. It would also be advantageous to allow subscribers toprovision call routing and billing information via the Internet.

The present invention overcomes the problems associated with the priorart.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is further described in the detailed descriptionthat follows, by reference to the noted drawings by way of non-limitingexamples of embodiments of the present invention, in which likereference numerals represent similar parts throughout several views ofthe drawings, and in which:

FIG. 1 is an exemplary functional block diagram of a telecommunicationsnetwork, according to an aspect of the present invention;

FIG. 2 is an exemplary call flow diagram according to an aspect of thepresent invention;

FIG. 3 is a flowchart diagram of exemplary billing processing, accordingto an aspect of the present invention;

FIG. 4 is a flowchart diagram of exemplary SCP service logic, accordingto an aspect of the present invention;

FIG. 5 is an exemplary #XXX table, according to an aspect of the presentinvention; and

FIG. 6 illustrates an exemplary Web page of a service management system(SMS) that is used to access a subscriber data directory, according toan aspect of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In view of the foregoing, the present invention, through one or more ofits various aspects and/or embodiments is thus presented to provide anabbreviated dialing service that operates within an AIN environment.

Accordingly, one aspect of the invention is to provide a method ofbilling a subscriber for abbreviated dialing code calls placed by acalling party in an AIN telecommunications environment. The methodincludes receiving an incoming call at a terminating switch andlaunching a query in response to a request from the calling party toestablish a connection with the subscriber, the calling party havingdialed the abbreviated dialing code. The method further includesaccessing a service control point in response to the query anddetermining at the service control point an alternate billing numberbased upon the location of the calling party and the abbreviated dialingcode. The method further includes determining an automatic messageaccounting (AMA) number at the service control point and using thealternate billing number instead of an abbreviated dialing code AMArecord associated with the AMA number so that the subscriber is billedfor the call rather than the calling party.

The method may include appending a first module to the alternate billingnumber and appending a second module to the AMA number at the servicecontrol point, sending the alternate billing number with the firstmodule and the AMA number with the second module to the switch, and thensending the alternate billing number with the first module and the AMAnumber with the second module to a billing system.

The method may also include directing the billing system to bill thesubscriber for the call based on instructions defined by the firstmodule. Further, the method may include discarding the abbreviateddialing code AMA record based on instructions defined by the secondmodule. The discarding may further include cross checking the AMA numberin a billing table. The billing system may determine whether thealternate billing number and AMA number received from the switch matchdata in the billing system, indicating that alternate billing number andAMA number were received at the correct billing system.

Another aspect of the present invention is to provide a method ofbilling a subscriber for abbreviated dialing code calls placed by acalling party in an AIN telecommunications environment. The methodincludes receiving an incoming call at a terminating switch andlaunching a query in response to a request from the calling party toestablish a connection with the subscriber, the called party havingdialed the abbreviated dialing code. The method further includesaccessing a service control point in response to the query andtranslating the abbreviated dialing code into a toll free number. Themethod also includes determining at the service control point analternate billing number based upon the location of the calling partyand the abbreviated dialing code, and also determining at the servicecontrol point an automatic message accounting (AMA) number.

Further, the method includes appending a first module to the alternatebilling number, appending a second module to the AMA number, sending thealternate billing number with the first appended module to the billingsystem, and the AMA number with the second appended module to thebilling system and then using the alternate billing number instead of anabbreviated dialing code AMA record associated with the AMA number sothat the subscriber is billed for the call rather than the callingparty.

The method may include instructing the billing system to bill theabbreviated dialing code service provider for the call based on thealternate billing number with the appended first module. Further, themethod may include directing the billing system to discard theabbreviated dialing code AMA record based on the AMA number with theappended second module. The discarding may include cross checking theAMA number in a billing table. The abbreviated dialing code may includea #XXX or #XX sequence.

Another aspect of the present invention is to provide atelecommunications system for processing calls placed by a calling partyto an abbreviated dialing code service in an AIN telecommunicationsenvironment. The system includes a service control point that derives analternate billing number with a first appended module and derives anautomatic message accounting (AMA) number with a second appended module.The system further includes a service switching point that receives thealternate billing number with a first appended module and AMA numberwith a second appended module from the service control point. Further,the system includes a billing system that receives from the serviceswitching point the alternate billing number and the AMA number, inwhich the billing system uses the alternate billing number to bill aprovider of the abbreviated dialing code service provider instead ofbilling the calling party.

The billing system may include a component that interprets the firstmodule as an instruction to billing the subscriber. The billing systemmay include a component that interprets the second module as aninstruction to discard an abbreviated dialing code AMA record. Further,the billing system may include a component that cross checks the AMAnumber in a billing table prior to discarding the abbreviated dialingcode AMA record. The billing system may also include a component thatdetermines whether the alternate billing number and AMA number receivedfrom the switch match data in the billing system.

Another aspect of the present invention is to provide a method forprovisioning an abbreviated dialing code service from a graphical userinterface. The method includes presenting to the subscriber at thegraphical user interface a subscriber data directory, in which thesubscriber data directory contains at least one abbreviated dialing codeand an associated state and local access and transport area (LATA). Themethod further includes receiving from the subscriber a toll free numberassociated with the at least one abbreviated dialing code and storingthe abbreviated dialing code, toll free number, state, and LATA in anAIN database. The subscriber may add, change, or delete a toll freenumber associated with the abbreviated dialing code.

Another aspect of the present invention is to provide a computerreadable medium for storing a computer program that processes billingfor a telephone call placed to an abbreviated dialing code. A recordingsource code segment is included that receives data from a switchassociated with a telephone call placed to the abbreviated dialing code,in which the data comprises at least an alternate billing number with afirst appended module and an automatic message accounting (AMA) numberwith a second appended module. A billing source code segment is includedthat uses the alternate billing number instead of an abbreviated dialingcode AMA record associated with the AMA number so that the calling partyif not billed for the call and the subscriber is billed for the call. Across checking source code segment may be included that cross checks theAMA number with a billing table to determine whether to discard anabbreviated dialing code AMA record.

The present invention is an AIN based system and method for translatingan abbreviated dialing code into a ten digit toll free number, routingthe call to an Interexchange Carrier (IXC), and managing the billingassociated with the call. The IXC will in turn route the call to acustomer call center or retailer. Once the call reaches the customercall center, a representative will ask the caller what product, companyor advertiser they desire, and then the customer call center will routethe call to the respective company or advertiser via thecompany/advertiser's toll free number. An important feature of thepresent invention is that the caller does not incur any chargesassociated with the call. Charges associated with the call are billed tothe subscriber.

As used herein, the term caller refers to the person originating atelephone call. The term subscriber is defined as the service providerof the abbreviated dialing code and operator of the customer callcenter. The subscriber will offer their service to mostly, but notexclusively, large national advertisers or companies who generallyemploy radio and outdoor advertising methods to reach their particularmarket. Also, the term access code may be used herein interchangeablywith abbreviated dialing code. Further, toll free numbers as discussedherein includes 800 and 888 numbers, as well as any future toll freenumber assignments.

FIG. 1 illustrates an exemplary telecommunications network of thepresent invention. The network 1 includes a calling party 10, a ServiceSwitching Point (SSP) 15, a Signal Transfer Point (STP) 20, a ServiceControl Point (SCP) 25, a toll free database 30, an IXC 35, a customercall center 40, and a billing system 50.

The SSP 15 is the originating central office (CO) for the caller. TheSSP 15 triggers when it receives an abbreviated dialing code and thensends a query to the SCP 25. The SSP 15 may comprise, for example, 1AESSor 5ESS switches manufactured by Lucent Technologies, or DMS-100switches manufactured by Nortel Networks Corporation (Nortel), or AXE-10switches manufactured by Telefonaktiebolaget LM Ericsson. The 1AESSswitches may use an AIN Release 0.1 protocol and should be equipped withGeneric 1AE13.01 (or higher) software and associated AIN SSP features.The 5ESS switches may utilize an AIN Release 0.1 protocol and should beequipped with Generic 5E12 (or higher) software and associated AIN SSPfeatures. The DMS-100 switches (release NA009) may utilize an AINRelease 0.1 protocol and associated AIN SSP features. The AXE-10switches may utilize an AIN Release 0.1 protocol and should be equippedwith Generic 8.07 (or higher) software and associated AIN SSP features.

The call service logic of the present invention may be upgraded toaccommodate future AIN releases and protocols and future trigger types.Specifications of AIN Release 0.1 SSPs may be found in BellcoreTR-NWT-001285, Switch-Service Control Point (SCP) Application ProtocolInterface Generic Requirements, the disclosure of which is expresslyincorporated by reference herein in its entirety, as well as AdvancedIntelligent Network (AIN) 0.1 Switching Systems Generic Requirements(GR-1298-CORE, Issue 5, November 1999) and the Advanced IntelligentNetwork (AIN) Generic Requirements: Switch-Service Control Point(SCP)/Adjunct Interface (GR-1299-CORE, Issue 4, September 1997), thedisclosures of which are also expressly incorporated by reference hereinin their entireties.

While SCPs are primarily discussed and referred to and shown in one ormore of the accompanying drawings, it is noted that an IntegratedService Control Point (ISCP) may be employed as well, and that the termsare used interchangeably herein. It is further noted that SCPs/ISCPs maybe deployed in mated pairs to ensure survivability and reliability ofthe network.

Exemplary service control points include the Telecordia IntegratedService Control Point Current Generation Platform (ISCP) (CGP) withRelease version 5.0.9.13; the ISCP Next Generation Platform (NGP) withRelease version 6.4.2.1; and the Lucent Service Control Point (LSCP)with Release 94 and Service Package Application Version 6 (SPA V6) orlater. The interface between the service switching points and theservice control point may be the Telecordia AIN GR-1299, entitled“Switch-Service Control Point (SCP)/Adjunct Interface.”

The messages transmitted between the SSP 15 and SCP 25 are all formattedin accordance with the Signaling System 7 (SS7) transaction capabilitiesapplications protocol (TCAP). Integrated Services Digital Network UserPart (ISUP) signaling is utilized between the central offices.

The SCP 25 stores information provisioned by the subscriber including800 routing number information for each of the subscriber's designatedabbreviated dialing codes. The SCP service logic derives thesubscriber's 800 routing number designated for the LATA in which thecall originates. The 800 routing numbers are entered into a database bythe subscriber as will be discussed later. Also, the SCP 25 storesinformation associated with the calling party such as the calling partyID (calling party number), LATA, and the name of the state in which thecaller resides. More specifically, an NPANXX table is maintained whichdetermines the LATA and state of the caller based upon the NPANXX of theoriginating call. It is necessary to determine the state name for properrouting to the correct customer call center since some LATAs encompassmore than one state.

For billing charges to the subscriber, the SCP service logic derives andreturns an alternate billing number associated with the subscriber'sabbreviated dialing code for the state and LATA in which the calloriginated. The alternate billing number is used to bill chargesassociated with the call to the subscriber's account. The SCP servicelogic also derives and returns an Automatic Messaging Accounting (AMA)number (i.e., AMA slpID) that is designated for each abbreviated dialingcode. The AMA slpID is used so that the caller is not billed for callingthe abbreviated dialing code. A module (i.e., index) associated with andappended to the alternate billing number and AMA slpID directs thebilling system 50 to utilize these parameters in processing the billing.Both the alternate billing number and AMA slpID are obtained at the SCP25 via a database lookup in an #XXX table, as will be discussed later.

Additional functionality associated with the SCP 25 includes requestinginformation from other network elements. In this regard, the SCP 25receives and processes SSP query messages, generates and sends messagesin response to the SSP queries, and generates counts of abbreviateddialing code call information.

The toll free database 30, upon request by the SSP 15, returns anappropriate IXC carrier identification code (CIC) assigned to the 10digit toll free number previously determined by the SCP 25. The queryalso returns the standard toll free billing (i.e., AMA) parameters. TheIXC CIC code and appended 10 digit toll free number are used to pass thecall to the IXC 35.

The IXC 35 takes the call handed to it by SSP 15 and routes it to thecustomer call center 40. A representative at the customer call center 40prompts the caller for the company or advertiser desired by the caller.Based upon the caller's response, the call is routed using thecompany's/advertiser's toll free number.

The billing system 50 is a computer data processing system that inputsappropriate charges on the subscriber's account and also discardsbilling records associated with end users of the abbreviated dialingcode service. The billing system 50 receives AMA records and other datafrom the SSP 15 that help facilitate the billing process, as will beexplained herein.

The abbreviated dialing code consists of, e.g., a #XXX or #XX dialingsequence as entered by the caller, rather than the conventional 7 or 10digit number sequence. Due to limitations associated with 1AESSswitches, 2 digit codes (e.g., #XX) are used in areas where 1AESSswitches are implemented. Unless otherwise indicated, #XXX and #XX willbe used interchangeably herein. The #XXX service is implemented usingthe following number assignments #000, #111, #227, #265, #289, #328,#333, #349, #359, #363, #444, and #849. However, it other numberassignments may be employed. Regarding 1AESS switches, the two digitcodes are translated into the appropriate three digit codes at the SCP25. The #XX service may be implemented using number assignmentsincluding 00, 11, 22, 26, 28, 32, 33, 34, 35, 36, and 84. However, it ispossible that other number assignments may be employed. A standardannouncement will be provided by the SSP 15 in the event that the dialednumber is invalid or otherwise out of service.

The #XXX service employs a Public Office Dialing Plan (PODP) featurecode trigger that will be provisioned on all caller lines permitted toaccess the #XXX service in all AIN equipped digital offices. That is,the trigger must be set for all lines in a switch for the service tofunction. The PODP feature code trigger, and #XXX service, arecompatible with vertical service code logic. Additional triggerscompatible with this service include an Off-Hook Delay (OHD) trigger anda Vertical Service Code (VSC) trigger. Vertical service code logic,accessed utilizing one of the aforementioned triggers at the SSP 15,performs the call processing for the #XXX service. Further informationregarding this is detailed in Bellcore GR1298-CORE, noted above.

FIG. 2 illustrates an exemplary call flow diagram of the presentinvention. At step 1, a caller dials an abbreviated dialing code (e.g.,#XXX) to reach a company or national advertiser. At step 2, a trigger onthe caller's line sends a query from the end office SSP 15 through theSTP 20 (not shown in FIG. 2) to the SCP 25, which queries an internalAIN database. The SCP service logic will be discussed in more detailwith respect to FIG. 4. The AIN database at the SCP 25 recognizes the#XXX number and translates it to the appropriate ten digit toll freenumber based upon the calling party ID, state, and LATA of the caller.These parameters are obtained using the NPANXX of the caller andperforming a lookup in an NPANXX table. Also at step 3, the SCP 25returns an alternate billing number and AMA slpID to the SSP 15 basedupon the subscriber's abbreviated dialing code and the state and LATA inwhich the call originated. These parameters are obtained via a lookup ina #XXX table.

From the AIN database of the SCP 25, the ten digit toll free number issent back through the STP 20 (not shown in FIG. 2) to the SSP 15 at step3. In response to the information received from the SCP 25, anabbreviated dialing code AMA record is created by the SSP 15 to bill thecharges associated with the use of the #XXX service. This record, an AINBellcore Automatic Message Accounting Format (BAF) record, is used tobill the subscriber on a minutes of use or per call charge basis for theabbreviated dialed service. The charges associated with the use of the#XXX service are billed to the subscriber in a customer recordinformation system (CRIS). The abbreviated dialing code AMA record issent (as will be discussed with respect to step 8) from the SSP 15 to aregional accounting office having a billing system, e.g., AmeritechCustomer Information System (ACIS). The billing system is a computerdata processing system that, among other things, inputs appropriatecharges on the subscriber's account. The abbreviated dialing code AMArecord may be transmitted to the regional accounting office by varioustelecommunications systems, for example, FTP, WAN, TCP/IP, fiber optic,etc.

At step 4, the SSP 15 queries the toll free database 30 where anappropriate IXC CIC code is attached to the ten digit toll free numberand the number is sent back to the SSP 15 at step 5. At this point, anaccess charge AMA record is created by the SSP 15 to bill 800originating access charges to the IXC that transports the call to the800 number of the subscriber. The 800 originating access charges areprocessed by the billing system 50 and are billed to the IXC using acarrier access billing system (CABS). The access charge AMA record issent (as will be discussed with respect to step 8) from the SSP 15 to aregional accounting office having a billing system, e.g., ACIS. Aspreviously mentioned, the billing system is a computer data processingsystem that inputs appropriate charges on the subscriber's account. Theaccess charge AMA record may be transmitted to the regional accountingoffice by various telecommunications systems, for example, FTP, WAN,TCP/IP, fiber optic, etc.

Additionally, at step 6, the SSP 15 hands the call off to theappropriate IXC 35 as identified by the toll free database 30. At step7, the IXC 35 routes the call to the customer call center 40.Thereafter, a representative at the customer call center will ask thecaller what product, company or advertiser they are interested in. Basedupon the caller's response, the representative directs the call to berouted to the respective company or advertiser via thecompany/advertiser's toll free number.

At step 8, the abbreviated dialing code AMA record and the access chargeAMA record are sent from the SSP 15 to the billing system 50.Additionally, the SSP 15 sends the alternate billing number and AMAslpID to the billing system 50. The alternate billing number and AMAslpID are transmitted to the billing system, each with their ownappended module. As previously mentioned, these parameters are initiallypassed from the SCP 25 to the SSP 15. Based upon the alternate billingnumber and appended module, a record is made in the billing system 50indicating that a #XXX call was placed so that a charge may be incurredto the subscriber's account.

An example of the billing system processing will now be discussed withreference to the exemplary flowchart diagram of FIG. 3. At step s1, thebilling system 50 receives the abbreviated dialing code AMA record andthe access charge AMA record, alternate billing number, and AMA slpIDfrom the SSP 15. The alternate billing number and AMA slpID each have anappended module. The programming in the billing system recognizes eachmodule as an instruction to perform a specific function, as will bediscussed below.

At step s3, the billing system 50 processes the charges associated withthe access charge AMA record in a known manner. As previously mentioned,the access charge AMA record is used to bill 800 originating accesscharges in CABS to the IXC that transports the call to the 800 number ofthe subscriber.

At step s5, it is determined whether the data sent from the SSP 15 hasbeen sent to the correct billing system within a state. That is, in someof the larger states, such as Texas, the LATAs are widely dispersednecessitating distinct billing systems. Thus, in order to ensure properprocessing, downstream data sent from the SSP to a billing system mustcoincide. The alternate billing number and AMA slpID sent from the SSP15 are compared to unique alternate billing numbers and AMA slpIDsstored at the billing system. If alternate billing number and AMA slpIDsent from the SSP 15 do not match the data at the billing system anerror results at step s7 and processing terminates. Otherwise,processing continues at step s9.

At step s9, the billing system 50 reads the module appended to thealternate billing number as an instruction to perform a specifiedfunction. That is, the module instructs the billing system to use thealternate billing number to bill the subscriber. Specifically, thebilling system records an entry to the subscriber's account indicatingthat a #XXX call was placed, so that the subscriber can be billed foreach of the processed #XXX calls. The #XXX charges are billed in CRIS.As a result, the telecommunications carrier may recoup charges for the#XXX service from the subscriber.

At step s11, the billing system 50 interprets the module appended to theAMA slpID as an instruction to perform a specified function. That is,the module instructs the billing system 50 that the abbreviated dialingcode AMA record may be discarded so that the calling party (i.e., enduser) is not billed for the originating #XXX telephone call. As aresult, a cross check is performed using the AMA slpID and a freebilling table (FBT). The FBT contains the #XXX number and associated AMAslpID (e.g., 333 and 033300101, respectively), both of which werepreviously provisioned in the FBT by the telecommunications carrier. Across check is performed in the event that the #XXX is used for anotherservice, in which case the abbreviated dialing code AMA record shouldnot be discarded. If a match for the AMA slpID is located in the FBT,the access charge AMA record is discarded.

FIG. 4 shows an exemplary flowchart diagram of the SCP service logic,according to an aspect of the present invention. At step s2 a query isreceived at the SCP 25 including the NPANXX of the calling party. TheSSP 15 creates an Info_Analyzed message to send to the SCP 25 when a VSCor PODP trigger is encountered. If an OHD trigger is encountered, theSSP 15 creates an Info_Collected message to send to the SCP 25. Ineither situation, the parameters expected by the service logic includeaccess code, vertical service code, redirection information, and callingparty ID. The access code and vertical service code parameterscorrespond to the #XXX number assignment, or any other special dialingsequence service provided by the telecommunications provider, e.g., *98.The redirection information parameter is populated when a calling partywith active call forwarding places a #XXX call from the forward tonumber. In this scenario, the redirection information is populated withthe calling party's original telephone number. The calling party IDparameter is the telephone number of the calling party.

In response to the query, at step s4 an NPANXX table is used to derivethe LATA and state of the calling party based upon what NPANXX the calloriginated from. An exemplary layout of the NPANXX table is shown belowas Table 1. The table includes an NPANXX column, a LATA column and aSTATE column. The NPANXX column stores either an NPA or an NPANXX. TheLATA column stores a 3 digit LATA, and the STATE column stores the statename or District of Columbia. Such a table should include all NPANXXs inthe service area, so that all lookups will find a match. The index intothe NPANXX table is the NPA or NPANXX of the calling party. As a resultof a lookup in the table, the state and LATA corresponding to the NPANXXof the calling party telephone number are retrieved. TABLE 1 NPANXX LATASTATE 312 358 ILLINOIS 328225 229 WISCONSIN 317227 432 INDIANA 313342589 MICHIGAN 330343 832 OHIO

At step s6 a determination is made as to whether an #XX or #XXX code wasreceived at the SCP 25. If an #XXX code was received, processingcontinues at step s10. At step s6, if an #XX code was received, alook-up is performed in a table at step s8 where a digit is retrievedand appended to the end of the XX string. A #XX code may be receivedwhen the service is accessed via a 1AESS office.

If an #XX code is received, a Global Information Table is accessed toascertain an additional digit. Although each subscriber to the #XXXservice is assigned the complete three digits, because the calloriginated from a 1AESS office, only the #XX is received at the SCP 25.The index, which is used for searching the Global information Table whenonly 2 digits have been received, is 1 plus the first two XX digits ofthe three assigned XXX digits plus the LATA of the calling party. Forexample, if the #XXX code is 123 in LATA 425 and the digits received atthe SCP 25 are #12, the index for this code is 1+12+425 or index=112425.Each entry in the index field of this table requires additional entriesin a Code Last Digit field. The Code Last Digit field is populated whenan index for a 1AESS office is entered for an XX code. This field willcontain the third digit of a #XX code. For example, if a caller dials#123 from a 1AESS office in LATA 425, the SCP 25 receives #12 and LATA425. In the Global Information Table, index 112425 is populated and theCode Last Digit field is populated with a 3.

When all three digits are present, at step s10 an index for a telephonenumber and billing information lookup is created. An exemplary indexincludes the XXX digits prefixed to the state name, with the LATAappended thereto. For instance, an access code of 333 with a callingparty in Illinois and LATA 358 would create an index equal to333ILLINOIS358.

Based on the index, at step s12 the called party ID is found in a table.That is, the called party ID parameter is set to the toll free telephonenumber assigned by the subscriber to the received dialed XXX code, stateand LATA. Also, at step s12 the AMA slpID is set based on the index.That is, the AMA slpID parameter is set to the AMA slpID numberassociated with the dialed XXX code, and the state and LATA associatedwith the calling party. Additionally, at step s12 the alternate billingnumber is determined based on the index. That is, the alternate billingnumber parameter is set to the alternate billing number associated withthe dialed XXX code, and the state and the LATA of the calling party.

FIG. 5 is an exemplary layout of an #XXX table. The table includes a#XXX column, LATA column, State Name column, Routing Number column, AMAslpID column, and an Alternate Billing Number Column. The Routing Numbercolumn contains the toll free number of the subscriber of the #XXXservice. The AMA slpID column contains the AMA slpID, which ispreferably composed of a leading zero, followed by the digits of the#XXX code, and followed by five additional digits (usually zeroes orones). One AMA slpID is associated with each #XXX code. A separatealternate billing number is provided for each #XXX within a particularLATA.

At step s14 the SCP 25 returns a response to the SSP 15. The response isan Analyze_Route message if all of the service criteria are met tovalidate call completion on the vertical service code or access codedialed. The significant parameters included in the Analyze_Routeresponse are the calling party ID, called party ID, AMA slpID, andalternate billing number. A Send_to_Resource response is returned whenthe vertical service code or access code is invalid. TheSend_to_Resource response causes the switch 15 to play a message to thecalling party, such as “We're sorry, we cannot complete your call asdialed. Please hang up, check the number and try again.”

FIG. 6 is an exemplary Web page 100 of a service management system (SMS)that is used to by a subscriber to access a subscriber data directory.The SMS may be accessed using, for example, Internet Explorer, version4.0 or higher, or Netscape, version 4.7 or higher. The SMS is capable ofaccepting information from a Web interface which will be used toprovision the #XXX information, LATA, state name, toll free number ofthe subscriber, and the alternate billing number in the SCP 25. The dataentered in the SMS is transmitted and stored on a partitioned databasein the SCP 25, where it is the source of the data located in the #XXXtable of FIG. 5. The subscribers will be permitted access to the SMS toinitially set up their 800 number information associated with each #XXXnumber; however, the subscriber will not see nor have access to thealternate billing number. Prior to the subscriber setting up the tollfree information, the alternate billing number, AMA slpID, LATA, andstate name are entered into the SMS by the telecommunications carrier.One 800 number is required to be entered by the subscriber for each LATAin which an #XXX service is offered.

To ensure that usage is directed to the correct billing system, at leastone alternate billing number is assigned and provisioned in the AINplatform for each LATA in which the #XXX service is deployed. If a LATAcrosses state boundaries, two alternate billing numbers will be assignedand provisioned per LATA. If a particular #XXX service is offered tomore than one subscriber, a different set of alternate billing numbersand toll free numbers will be required for each subscriber.

Subscribers will be able to make changes to the SMS, which will beviewable by the subscriber on a real time or near real time basis. TheSMS provides the ability to view metrics pertaining to the service viatables or graphs, without viewing the services provided to othersubscribers. Other features of the SMS include troubleshooting, storageof performance statistics, and performance metrics on a per user basisto analyze service performance.

Login to the SMS requires entering a user name consisting of a 10 digittelephone number from the subscriber's POTS line and the subscriberpassword. After validation as a user, the subscriber is presented with amessage screen which displays any new messages of information that maybe important to the subscriber. A define capability screen 100 as shownin FIG. 6 allows a subscriber to add, delete, or change 800 numberinformation in the subscriber data directory for each access code andLATA. The functionality of the define capability screen 100 also permitsthe subscriber to view records, search by access code, LATA, state, or1-800 number.

Define capability screen 100 contains table 101 and text box 102. A newrecord may be added by the subscriber by clicking on new record icon103. Table 101 includes an access code column 105 that contains all ofthe #XXX codes for a particular subscriber. A LATA column 106 containsall of the LATAs associated with the access codes in column 105. A phonenumber column 107 contains the toll free number associated with theaccess code and LATA of columns 105 and 106. A state column, not shown,contains the state name associated with the information in columns 105,106, and 107. A state identifier such as an abbreviation may be providedin lieu of the entire state name.

Mini icons in column 108 allow selection of a particular access code,with associated LATA, state, and phone number for updating or deletinginformation. By selecting a mini icon in column 108, the particularaccess code, with associated LATA, state, and 800 number appears in textbox 102. The 800 number may be changed or new 800 numbers may be addedby entering 800 number information in phone number text box 110. Bulkchanges to the subscriber data directory may be accomplished via filetransport protocol (FTP). Various other functions are included on thedefine capability screen including a cancel button 111 that terminatesthe current set of updates and discards all of the changes made during aparticular session. A previous button 112 is provided that returns thesubscriber to a previous screen, i.e. a service object screen (notshown). The service object screen displays to a subscriber the #XXXservices to which they subscribe. An update button 113 is provided toenter the information in phone number text box 110 into table 101. Areset button 114 is provided to clear the contents of the phone numbertext box 110 and a next button 115 takes the user to a work ordersscreen (not shown). The work orders screen displays all of the changesthat have been input into define capability screen 100.

Several search tools may be accessed at the define capability screen,i.e., key search tool 120, field search tool 121, and range search tool122. Key search tool 120 allows a search for an 800 telephone number.Clicking on key search tool 120 displays a text field for the number tobe entered. After entering all 10 digits of the 800 number and clickingthe search button, the information corresponding to the 800 number willbe displayed in a data table. The field search tool 121 allows a searchof the access code data by LATA, state, phone number, or access code.Also, field search may be used to find all access codes beginning withthe same digits or characters, e.g., searching for all LATAs and 800numbers associated with 333 access codes. The procedure for using thefield search tool 121 includes clicking on the field search button,selecting the type of search (e.g., access code or LATA), selecting asorting criteria (i.e., access code, LATA, state, or phone number), andselecting an operator (e.g., equal, less than, etc.). The range searchtool 122 allows a search for all access codes in a given range or asearch for LATAs within a numeric range (e.g., from 333 to 555). Theprocedure for using the range search includes clicking on the rangesearch tool 122, and entering either the desired range in the accesscode fields or LATA fields and clicking on the search button.

A logout button (not shown) is provided on certain screens of the SMS.Additionally, an automatic logout is performed after a predeterminedperiod of inactivity.

Although the invention has been described with reference to severalexemplary embodiments, it is understood that the words that have beenused are words of description and illustration, rather than words oflimitation. Changes may be made within the purview of the appendedclaims, as presently stated and as amended, without departing from thescope and spirit of the invention in its aspects. Although the inventionhas been described with reference to particular means, materials andembodiments, the invention is not intended to be limited to theparticulars disclosed; rather, the invention extends to all functionallyequivalent structures, methods, and uses such as are within the scope ofthe appended claims.

In accordance with various embodiments of the present invention, themethods described herein are intended for operation as software programsrunning on a computer processor, including switches, etc. Dedicatedhardware implementations including, but not limited to, applicationspecific integrated circuits, programmable logic arrays and otherhardware devices can likewise be constructed to implement the methodsdescribed herein. It should also be noted that the softwareimplementations of the present invention can be stored on a tangiblestorage medium such as a magnetic or optical disk, read-only memory orrandom access memory and be produced as an article of manufacture.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the invention is not limited to such standards andprotocols. Each of the standards for AIN and public telephone networks(ISDN, ATM, xDSL) similarly represent examples of the state of the art.Such standards are periodically superseded by faster or more efficientequivalents having essentially the same functions. Accordingly,replacement standards and protocols having the same functions areconsidered equivalents.

1. A method in an AIN telecommunications environment of identifying asubscriber to bill for an abbreviated dialing code call placed by acalling party, the method comprising: receiving an incoming call inresponse to the calling party having dialed the abbreviated dialingcode; translating the abbreviated dialing code to a toll free numberassociated with the abbreviated dialing code; sending a query to aservice control point to determine first and second parametersassociated with the abbreviated dialing code; and using the firstparameter to bill the subscriber of the abbreviated dialing code for thecall rather than the calling party, wherein the toll free number isassociated with the subscriber to be billed for the call placed to theabbreviated dialing code.
 2. The method according to claim 1, furthercomprising: using the second parameter to discard an abbreviated dialingcode automatic message accounting record associated with the secondparameter.
 3. The method according to claim 1, further comprisingsending the first parameter to a billing system.
 4. The method accordingto claim 1, further comprising sending the second parameter to a billingsystem.
 5. The method according to claim 1, the first parameter furtherbeing associated with a subscriber's abbreviated dialing code for thestate and LATA in which the call originated.
 6. The method according toclaim 1, wherein the first parameter comprises an alternate billingnumber.
 7. The method according to claim 1, wherein the second parametercomprises an automatic messaging accounting number.
 8. The methodaccording to claim 1, wherein the abbreviated dialing code comprises a#XXX sequence.
 9. The method according to claim 1, wherein theabbreviated dialing code comprises a #XX sequence.
 10. Atelecommunications system for processing calls placed by a calling partyto an abbreviated dialing code service in an AIN telecommunicationsenvironment, comprising: a service control point that derives first andsecond parameters associated with a subscriber's abbreviated dialingcode; and a billing system that inputs charges associated withabbreviated dialing code calls on a subscriber's account and discardsbilling records associated with a calling party's use of the abbreviateddialing code service.
 11. The telecommunications system according toclaim 10, wherein the service control point stores informationprovisioned by the subscriber of the abbreviated dialing code service.12. The telecommunications system according to claim 10, wherein theservice control point derives a routing number of the subscriber thathas been designated for a particular LATA.
 13. The telecommunicationssystem according to claim 10, wherein the first parameter comprises analternate billing number.
 14. The telecommunications system according toclaim 10, wherein the second parameter comprises an automatic messagingaccounting number
 15. The telecommunications system according to claim10, further comprising a service switching point provisioned with apublic office dialing plan feature code trigger.
 16. Thetelecommunications system according to claim 10, further comprising aservice switching point that creates an abbreviated dialing code AMArecord in response to receiving the first and second parameters from theservice control point.
 17. The telecommunications system according toclaim 10, wherein the service control point translates the abbreviateddialing code to a toll free number.
 18. The telecommunications systemaccording to claim 10, wherein the abbreviated dialing code consists ofa #XXX or #XX sequence.
 19. A computer readable medium storing acomputer program that identifies a subscriber to bill for an abbreviateddialing code call placed by a calling party, the program comprising: areceiving code segment that receives an incoming call in response to thecalling party having dialed the abbreviated dialing code; a translatingcode segment that translates the abbreviated dialing code to a toll freenumber associated with the abbreviated dialing code; a determining codesegment that determines first and second parameters associated with theabbreviated dialing code; and a billing code segment that uses the firstparameter to bill the subscriber for the call rather than the callingparty, wherein the toll free number is associated with the subscriber tobe billed for the call placed to the abbreviated dialing code.
 20. Acomputer readable medium for storing a program for processing billing ofan abbreviated dialing code call placed by a calling party, the programcomprising: a recording code segment that records information associatedwith a subscriber's abbreviated dialing code, the information comprisingat least a toll free number of the subscriber; a determining codesegment that determines first and second parameters associated with thesubscriber's abbreviated dialing code; and a billing code segment thatbills the subscriber for the call rather than the calling party, usingthe first parameter.
 21. A method in an AIN telecommunicationsenvironment of billing a subscriber for abbreviated dialing code callsplaced by a calling party, the method comprising: receiving an incomingcall in response to the calling party having dialed the abbreviateddialing code; translating the abbreviated dialing code to a toll freenumber associated with the abbreviated dialing code; determining analternate billing number based upon the location of the calling partyand the abbreviated dialing code, the determination occurring at theservice control point; and using the alternate billing number so thatthe subscriber of the abbreviated dialing code is billed for the callrather than the calling party, wherein the toll free number isassociated with the subscriber to be billed for the call placed to theabbreviated dialing code.